Arcserve® Unified Data Protection Version 5.0 Release Notes

4.0 System Information
4.1 Windows System Requirements
4.2 Arcserve UDP Agent (Linux) System Requirements
  4.2.1 Arcserve UDP Agent (Linux) Server
  4.2.2 Arcserve UDP Agent (Linux) Backup Node
  4.2.3 Arcserve UDP Agent (Linux) Target Node
  4.2.4 Arcserve UDP Agent (Linux) Live CD
4.3 Operating System Support
4.4 Desktop and Laptop Support
4.5 Application Recovery Support

5.0 General Considerations

6.0 Issues Fixed

7.0 Known Issues

8.0 Compatibility Issues with Arcserve UDP Agent (Linux)

9.0 Limitations

10.0 Language Support

11.0 Acknowledgements

1.0 Welcome

Welcome to the Arcserve Unified Data Protection (Arcserve UDP) Release Notes. This document contains the following information related to the use of Arcserve UDP:

High-level description of the major features.

System information and other requirements you must know before installation of this solution.

A list of considerations, known issues, documentation issues, and limitations to be aware of before you use this solution.

2.0 Features

The Arcserve UDP solution provides an all-inclusive solution for next-generation storage problems of organizations that are trying to protect their data in a rapidly changing virtual, cloud, and services world. The solution does this by providing a single user interface to a wide range of functionality addressing multi-site business continuity and disaster preparedness problems.

The following features and functionality are provided:

Recovery Point Server (RPS) – This is an intelligent storage-target gateway which can be used to offload resource-intensive tasks from the Arcserve UDP Agent (Windows), such as catalog generation and merge/purge operations. This gateway can be used as a local storage center and also as a replication engine for multi-site data protection to remote locations (taking advantage of global source-side data deduplication functionality). You can build multiple storage targets (Data Stores) on a Recovery Point Server.

Data Deduplication – The Recovery Point Server gateway provides source-side data deduplication capability. Data deduplication enables integrated site-to-site replication so that only the data that has changed is backed up from the source to the local intelligent target and then transferred between intelligent targets located at different sites. Higher deduplication rates are achieved when backing up multiple nodes to the same Data Store with Deduplicate Data enabled or the nodes with lots of free space.

Integrated Replication – The Arcserve UDP solution supports site-to-site replication (over LAN and WAN) between Recovery Point Servers. Resume replication is also supported in case an error occurs and interrupts the replication process.

Microsoft Hyper-V Support – The Arcserve UDP solution performs agentless backups of data that reside on virtual machines running on Microsoft Hyper-V without installing the Arcserve UDP Agent (Windows) on the source virtual machines. Incremental backups are supported to back up only the changed data. Compression and deduplication are supported in the backup to decrease the backup size. Virtual Standby is also supported on Microsoft Hyper-V.

VMware vSphere Support – The Arcserve UDP solution performs agentless backups of data that resides on virtual machines running on VMware vSphere (including the newest version VMware vSphere 5.5) without installing Arcserve UDP Agent (Windows) on the source virtual machines. Incremental backups are supported to back up only the changed data. Compression and deduplication are all supported in the backup to decrease the backup size. Virtual Standby is also supported on VMware vSphere.

Protect Windows nodes – Performs disk-based backups through Arcserve UDP Agent (Windows) running on the node. The node can be a laptop, physical machine or virtual machine on VMware vSphere and Microsoft Hyper-V, including the newest version Windows Server 2012 R2 and Windows 8.1.

Protect Linux nodes – Performs disk-based backups on Linux nodes through Arcserve UDP Agent (Linux) Backup Server. The node can be laptop, physical machine or virtual machine running on VMware ESX server, Citrix Xen Server, Oracle VM, and Red Hat Enterprise Virtualization.

Integrate with Arcserve Replication and High Availability – Provides the capability to manage and monitor Arcserve Replication and High Availability functions from the Arcserve UDP Console.

Integrate with Arcserve Backup - The Arcserve UDP solution provides the capability to utilize a complimentary, limited version of Arcserve Backup to perform backups (agent-based and agentless-based) to tape.

Share Plan with Remote Recovery Point Servers – Allows you to map multiple Windows users with specific Plans. You can create a Plan as you receive replicated data from the remote Recovery Point Server. These Plans can be mapped with the Windows account and shared with Remote Recovery Point Servers.

Protect Nodes through Plan – A Plan is a series of tasks that are assembled together to provide data protection. These tasks can include performing Agent-Based Backups, Host-Based Agentless Backups, creating a Virtual Standby machine, Replications, Copying of Recovery Points, and Copying of Files. The Plan can be deployed for protecting multiple nodes and can be enabled or disabled. You can also set email alerts in the Plan for job success, failure, and so on.

Multiple Data Store Options – Data Store is used by Recovery Point Servers as a location for storing backed-up data. The storage location can be a local disk, a remote share folder, or a NAS device. Data Stores provide plenty of options for data security and space efficient usage. Compression and global data deduplication are supported in data stores to help decrease the size of created backups. Encryption is also supported to provide security for the backed-up data.

Advanced Schedule – Allows you to set different schedules for performing backup jobs, merging, throttle, and replication jobs for each day. Also allows you to specify daily/weekly/monthly retention periods.

Virtual Standby –Creates a standby virtual machine for the source node where the most recent recovery points of a source are represented by VM snapshots. Provides capability to power on virtual machine manually or automatically when the source node is not available after disaster. Supports the newest version of hypervisors (VMware vSphere 5.5, Windows Hyper-V 2012 r2). Supports greater than 2 TB disks through VMware ESX(i) server 5.5 or Hyper-V VHDX format virtual disks.

Create Reports – Collects information and allows you to view reports about such information as Managed Capacity of backup, Backup Size, Backup Status, Virtualization Protection Status, and Data Distribution on Media.

Multiple Data Recover Options – Allows you to recover data at the application level, the file level, and the VM level. For Arcserve UDP Agent (Linux) it also allows instant volume level recovery.

Granular Restore for Exchange - The Arcserve UDP solution supports the restore of Exchange mails of an account, a mail folder, or a single mail for Exchange 2013, Exchange 2010, and Exchange 2007.

Bare Metal Recovery (BMR) – Provides the capability to recover a computer system from “bare metal” including the operating system, applications and data components necessary to rebuild or restore the entire backed-up system. BMR is used for disaster recovery or for migration from one server to another. The Arcserve UDP solution provides the capability to perform V2P (Virtual to Physical) Bare Metal Recovery from the Arcserve UDP Agent (Windows) backup session, from the latest state of a standby virtual machine, from any recovery point that has been previously converted from a Arcserve UDP Agent (Windows) backup session, and from the host-based backup session. The Arcserve UDP solution also supports performing a Preboot Execution Environment (PXE)-based BMR from Arcserve UDP Agent (Linux) backup sessions. Arcserve UDP also supports BMR from an ISCSI destination.

Copy Recovery Point – Creates a copy of a recovery point to the specified destination for added data protection.

File Copy – The Arcserve UDP solution provides the capability to copy/move files to and from the cloud or disk for added data protection.

Central License Management – Arcserve UDP licenses are installed on and checked centrally on the Arcserve UDP Console. With central license management, the license allocation is server based. This means that when a license is allocated to a server, central license management will record this allocation and keep this license exclusively used for that server. Future license requests from the same server will always succeed, and requests from other servers will cause a new license to be allocated to the new server. When there are no licenses available, you will get an activity log message warning you that the license is a problem.

RPS Jumpstart – RPS Jumpstart lets you copy data to be replicated to an external device and then from the device to the remote RPS server. It is an effective method for transferring a large amount of data with low network bandwidth.

3.0 Product Updates

The following Arcserve UDP Release Notes updates are available for this release:

Update 1

Update 2

Update 3

Update 4

Updates are cumulative and can be installed on any previous version of Arcserve UDP.

4.0 System Information

This section describes the system requirements and supported operating systems. Review this information before installing and using Arcserve UDP.

4.1 Windows System Requirements

The minimum system requirements are:

CPU:
- Arcserve UDP Console: 1 GHz or higher processor is recommended
- Arcserve UDP RPS Server: 4 logical CPU's with a 2.7 GHz or faster processor recommended
- Arcserve UDP Agent (Windows): 1 GHz or faster processor recommended

RAM:
- Arcserve UDP Console: 4 GB or more is recommended
- RPS Server: 8 GB RAM or more recommended
- Arcserve UDP Agent (Windows): 1 GB or more recommended

Disk Space Requirements:
- Installation of arcserve_Unified_Data_Protection_Agent.exe
  2 GB (minimum)
  
  2.5 GB or more (recommended)
  
  Temporary folder 2 GB for setup
  
  System drive 300 MB for shared components
- Installation of arcserve_Unified_Data_Protection.exe
  5 GB (minimum)
  
  7 GB or more (recommended)
  
  Temporary folder 3 GB for setup
  
  System drive 2 GB for shared components

Host-Based VM Backup:
- Arcserve UDP backup proxy for agentless backup: 4 logical processor or more, 8 GB RAM or more are recommended.
- To run functions such as Preflight Check, pre/post commands, or application log purge, use one of the following credentials for the guest virtual machine:
  - Built-in administrator user credentials.
  - Built-in domain administrator user credentials.
  - For other administrator credentials, disable the User Account Control (UAC) on the guest virtual machine.

Other Hardware

CD/DVD ROM Drive (necessary when installed from a CD/DVD)

XGA (1024 x 768) or higher-resolution video adapter and monitor

Internet Browser

For a complete list of all supported Internet browsers, see the Compatibility Matrix.

Adobe Flash Player

Adobe Flash Player 10 or later
Note: Adobe Flash Player is needed on the computer from where the Arcserve UDP Agent (Windows) server is accessed. This can be the Arcserve UDP Agent (Windows) server itself or any other remote computer.

4.2 Arcserve UDP Agent (Linux) System Requirements

The following topics contain the Arcserve UDP Agent (Linux) system requirements.

4.2.1 Arcserve UDP Agent (Linux) Server

Review the system requirements for the Linux server where you install Arcserve UDP Agent (Linux).

Operating System

For a complete list of all supported server operating systems, see the Compatibility Matrix.

Memory

1024 MB minimum

Disk Space

1.2 GB minimum where the /tmp folder is located

1.2 GB minimum where the /opt folder is located

Web browser to manage the Arcserve UDP Agent (Linux) server

For a complete list of all supported web browsers, see the Compatibility Matrix.

Minimum Resolution

1024*768 pixels

4.2.2 Arcserve UDP Agent (Linux) Backup Node

Review the following system requirements for the backup source node:

Operating System and Architecture

For a complete list of all supported server operating systems for physical and virtual machines, see the Compatibility Matrix.

Memory

512 MB minimum

File System

Ext 2/3/4

ReiserFS v3

4.2.3 Arcserve UDP Agent (Linux) Target Node

Review the following system requirements for the target node where the data is restored.

Architecture

64 bit

4.2.4 Arcserve UDP Agent (Linux) Live CD

Review the following system requirements for the Live CD running environment:

Operating System

Physical and virtual machines

Architecture

Memory

1024 MB minimum

4.3 Operating System Support

For a complete list of all supported server operating systems, see the Compatibility Matrix.

4.4 Desktop and Laptop Support

For a complete list of all supported desktop and laptop systems, see the Compatibility Matrix.

4.5 Application Recovery Support

For a complete list of all supported application recovery systems, see the Compatibility Matrix.

5.0 General Considerations

This section contains general information that you should know before using Arcserve UDP:

Backup Considerations

When integrating Arcserve UDP Agent (Windows) with Arcserve Replication and High Availability and replicating data, you may discover that a greater quantity of data is replicated from the Master server to the Replica server than the actual file size on the Master server. This behavior is known to occur when using the non-compressed and non-encrypted backup option. You can minimize the effects of this behavior by configuring the scenarios to replicate periodically.

Starting with Microsoft Exchange Server 2013, all public folders are stored under specially designed public folder mailboxes in the Mailbox database. Therefore, to back up public folders, back up the corresponding Mailbox database.

When you back up a Microsoft SQL instance from machine A and restore the Microsoft SQL instance to machine B, if the Microsoft SQL instance on either machine A or machine B is in windows authentication, and the database "master" is included in the restore list, the Microsoft SQL instance on machine B will fail to start after the restore.

To avoid possible failures (mainly for large backup jobs), the buffering I/O settings have been turned off by default. However, with buffering turned off, there can be a corresponding drop or slowdown in backup speed (I/O throughput). If you are performing small backup jobs and you want to increase job performance, you can manually turn on buffering as follows:
1. Locate and open the afstor.ini file (C:\Program Files\CA\arcserve Unified Data Protection\Engine\Configuration).
2. Change the three buffering settings from 0 (off) to 1 (on):
  - BufferingForLocal=0
  - BufferingForUSB=0
  - BufferingForRemoteFolder=0
  Note: This is valid for non-data store destinations with the backup format set to Standard.

The following actions or configurations may affect the size of the block-level backups because Arcserve UDP Agent (Windows) or host-based VM backup will continue to incrementally back up all changed blocks. This means that blocks that shifted due to those actions or configurations will also be included in the backup, even if no data has changed in the files. As a result, the backup size may increase. This is expected behavior. If you do not want the increased backup size, you can stop any schedules for defragmentation or exclude affected volumes for Arcserve UDP Agent (Windows) (volume exclusion does not apply to host-based VM backup).
- Volume defragmentation
- Volume is NTFS deduplication enabled
- System activities, such as page file or hibernation file IO (this applies to host-based VM backup only)

When using multiple backup destinations with the Arcserve UDP Recovery Point View on a single Arcserve UDP Agent (Windows) node, if you change one destination back to the normal Windows view, it will force dismount of all volumes mounted by Explorer Extension. To avoid this problem, you should delay changing views until you are done using all destinations that are shown in the Arcserve UDP Recovery Point View.
Note: This is only valid for non data store destinations.

When a backup job is running, do not try to shrink the volume being backed up. If you do shrink the volume during the backup, data from this session may not be used for data recovery and a Verify backup is necessary afterwards to ensure the data integrity.

If you are backing up volumes that were replicated using Arcserve Replication and High Availability, you should verify that the spool has been created on a separate volume and configure your backup settings to exclude the spool volume. This helps to avoid the backing up of unnecessary temp spool data.

After a Microsoft Exchange 2007 and Microsoft Exchange 2010 database backup, if its path is moved to a different location, restore from the session which is backed up before moving the path will fail.

If both compression and encryption are disabled, then Arcserve UDP Agent (Windows) can only back up the files in .VHD format; it cannot back up the files in .VHDX format.
Note: This is valid for non data store destinations with backup format as standard.

When Arcserve UDP Agent (Windows) backs up a Hyper-V server, the VMs might proceed to the Saved state for a short time when the backup job starts. This may lead to the VM in a temporary offline status, and will be back online within a few seconds. To prevent this condition, the VM should meet certain conditions.
Note: For more information, see http://msdn.microsoft.com/en-us/library/dd405549(v=vs.85).aspx.

Random data corruptions have been observed when backups are written to the following device and if a network connection is lost during backups or merges.
- Iomega StorCenter ix4-200d

The following considerations are applicable if you are using Arcserve UDP Version 5.0 Update 2 and you upgrade to Arcserve UDP Version 6.0. In Arcserve UDP Version 5.0 Update 2, when an agentless backup is performed on a Hyper-V VM that does not support an online backup, the VM is placed in an offline "saved state" while the snapshot is taken for the VM. After upgrading to Arcserve UDP Version 6.0, the default behavior while in this saved state is changed. As a result, consider the following items for Hyper-V agentless backups:
- Arcserve UDP has a new option to select the Hyper-V Snapshot Method. Additionally, Arcserve UDP Version 6.0 also changes the default behavior of the VM when an application consistent snapshot is denied, for both existing and new Host-based Agentless plans.
- The change in the default behavior is to help you decide when to perform a backup, based upon either having a short downtime (few seconds to 2 minutes) or a possible lack of data consistency.
- After the upgrade, if the existing backup jobs fail that were previously not failing, and you want to change the saved state behavior to the way it was in Update 2, you can modify the plan and allow for saved state backups.
- Review the VSS errors in the event log of the Hyper-V host machine for a detailed understanding and resolution of the error, and to enable VSS-supported online snapshots.

Bare Metal Recovery Considerations

The BMR process cannot create storage spaces.

Data Store Considerations

The Backup Destination Folder field, the Data Destination field, the Index Destination field and the Hash Destination field are empty, by default. A path that you specify can be created by Arcserve UDP, if it does not exist, or you can browse for a path that exists. The existing path must be empty.

A deduplication data store has 4 paths to specify: backup destination folder, data destination, index destination, and hash destination. If you do not leverage SSD to process hash keys, it is ok to configure all of the 4 paths on the same volume. If you do leverage SSD to process hash keys, configure the hash destination on SSD and other paths on the same volume. For exapmle:
- Pure memory mode: Configure all paths on the same volume.
- SSD mode: Configure the hash destination on SSD and other paths on the same volume.
To get better processing speed, you can configure these paths on different physical disks. For example:
- Pure memory mode: Configure data path on one volume (LUN), remaining three paths to another volume (LUN).
- SSD mode: Configure the hash destination on SSD, configure data path on one volume (LUN), remaining two paths to another volume (LUN).

To use Deduplication Data Store, ensure your recovery point server has enough memory. With assumption that protect 1TB unique data (if Deduplication ratio is 50%, then 2 TB of source data is protected) with 4KB deduplication block size, the estimated memory requirement is 8GB.

File Copy Considerations

File copy does not support copying files from Volume Mount Points and Nameless volumes (volumes which do not have a drive letter). The Arcserve UDP Agent (Windows) only performs file copy on mounted volumes that have an assigned drive letter.

File Copy to Cloud does not support machines where the name contains Japanese characters.

GUI Considerations (Agent)

If you change the structure of the database in Microsoft Exchange or Microsoft SQL Server (add, delete, or move the database), the GUI is not updated dynamically. The Arcserve UDP Agent (Windows) gets the latest information after the service is restarted.

When using Internet Explorer and you search a file or folder to restore, and there are many files or folders in the search result, Internet Explorer may display the message "A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?" Some scripts can take an excessive amount of time to run, so Internet Explorer prompts you to decide whether you would like to continue running the slow script. To resolve this issue, perform one of the following tasks:
- Modify the registry to change the script time-out value in Internet Explorer for specific client machines. For more information, see http://support.microsoft.com/kb/175500.
- Use another browser and try again.

The Arcserve UDP Recovery Point View (Agent Explorer Extension) does not support browsing and restoring a volume without a drive letter.

When using Internet Explorer 10, you may see some misplaced borders or distorted text on the GUI. This has no functional effect on use of the product, but if you would like a better viewing experience, try using Google Chrome or Mozilla Firefox web browsers.

You can log in to the Linux Backup Server from the Arcserve UDP Console only when you perform a restore.

High Availability Considerations

After adding Arcserve Replication and High Availability control service, the Arcserve UDP user interface could manage the scenarios, process Replication and High Availability engine remote deployment, register the licenses and generate the reports for that control service.

Only full system scenarios could be created via the scenario creation wizard in the Arcserve UDP user interface. Use the Replication and High Availability manager user interface to create other types of scenarios.

Only full system scenarios root directory could be edited in the Arcserve UDP user interface. Use the Replication and High Availability manager user interface to edit other types of scenarios.

In the Arcserve UDP user interface, the Replication and High Availability templates cannot be created, edited and used to create scenarios.

The following scenario operations are not supported in the Arcserve UDP user interface:
- Host maintenance
- Restore & rewind
- Offline sync
- Auto configuration
- Configure HTTP Proxy for Control Service

In the Arcserve UDP user interface, Amazon EC2 is not supported in full system scenarios.

The feature editing the properties for running scenarios is not supported in the Arcserve UDP user interface.

The report data on the high availability tab will update every one hour.

Installation/Uninstallation/Remote Deployment Considerations

The followings upgrade scenarios are not supported:
- Upgrading from Arcserve UDP Version 5.0 Alpha, Beta, or RC build.
Solution

If you have an Alpha, Beta, or RC build, uninstall it first.

If you install Arcserve UDP Agent (Windows) and uncheck the Install the Arcserve UDP Agent change tracking driver option and later decide to use this computer for performing backups, manually install the driver and then reboot the computer. You can access this driver from the Arcserve UDP Agent (Windows) home folder at the following location and you can run the install driver batch file:
"<Install Path>\Engine\BIN\DRIVER\InstallDriver.bat"

If you have the combination of Microsoft SQL Server 2012 SP1 (64-bit) and Microsoft SQL Management Studio, uninstall Microsoft SQL Management Studio before installing Arcserve UDP Agent (Windows). For more information, see Article 770630 on the Microsoft website.

License Considerations

If after opening the Central License Manager under the Arcserve UDP Help menu, no licenses are shown, then the product is in the 30 day free trial period.

Merge Considerations

During the merge job:
The column Data Protected of full backup in the section Protection Summary is displayed as the sum of source data size of all to-merge recovery points. Once the merge job is done, it will be displayed as the size of the newly merged full backup. This applies to all type of destinations.

The column Space Occupied of full backup in the section Protection Summary is displayed as the sum of the occupied disk size of all to-merge recovery points. Once the merge job is done, it will be displayed as the disk size of the newly merged full backup. This applies to only non-deduplicated data stores and non-data store destinations. (local disk or network share)

When a merge job runs, the following operations fail on the session which is in the same backup chain as the merge job.
- Mount recovery point.
- Restore browse and search, if the sessions do not have a catalog.

The merge job might fail if the following operations are performed before it runs:
- Mount recovery point. Dismount the mounted volumes and trigger a new merge job.
- Restore browse and search, if the sessions do not have a catalog. Do not perform Restore browse and search UI operations for 10 minutes, and then trigger a new merge job.
Note: When the backup is to a shared folder, you can click the Run a merge job manually now link in the Arcserve UDP Agent (Windows) UI home page Summary section to trigger a new merge job.

Plan Considerations

Only if your backup task destination is recovery point server, you can add a new replicate task. In other words, if the backup task destination is a local or remote share, you cannot add a new replicate task.

Replicate tasks support replication between all kinds of data stores except:
- Replication from a data store with Encrypt Data enabled to a data store without Encrypt Data enabled.
- Replication from a data store with Deduplicate Data enabled to a data store without Deduplicate Data enabled.

Restore Considerations

If the volume does not have a drive letter, restoring to the original location is not supported. The restore operation is blocked on the UI.

If a database or storage group is renamed or removed after a backup, restoring to the original location fails. Either restore from the latest recovery point or restore to the disk.

When restoring the Microsoft Exchange database to a relational database, select the relational database on the machine where the Microsoft Exchange database is backed up. If you want to restore the Microsoft Exchange database to the relational database on another machine, dump the database file onto that machine and attach it to the relational database.

Restoring a Microsoft Exchange database on to a database residing on a compressed volume or directory is not recommended or supported by Microsoft. This can lead to a dismounted state of the database after restore. As a workaround, move the database path to an uncompressed volume or directory before restore and perform the restore again. For more information see http://support.microsoft.com/kb/327772.
For best practices on NTFS compression in Windows, see http://support.microsoft.com/kb/251186.

If you change the password of the remote destination, update the password in Settings before submitting any restore jobs.

When you restore files on an NTFS volume with the encryption attribute, to a non-original backup computer, the file is not accessible. This inaccessibility is a system limitation. Also, note the following limitations:
- For a catalog restore, the job succeeds as normal, the file is restored, however it cannot be accessed.
- For a catalog-less restore, the job fails and the encrypted file is logged as inaccessible.

If the following conditions exist in a two node CCR cluster (cluster continuous replication), the database restore succeeds but the restore job has a status of "Failed":
- The active node is paused.
- A Arcserve UDP Agent (Windows) database restore to the original location is attempted from the active node.

If you are restoring a Microsoft SQL Server instance, the restore may be incomplete if you get the following error:
“the process cannot access the file because it is being used by another process”

Also, the SQL Server event log reports the following error with Event ID 8355:

“Server-level event notifications cannot be delivered. Either Service Broker is disabled in msdb, or msdb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker”.

If this occurs, free up some available memory or increase the memory to 4 GB or more.

On the restore Browse Recovery Points dialog, when you expand a directory that contains 50 or greater items, a pagination window displays. If you select that folder, and then you expand it but you do not browse all pages, only the items on the pages which have been browsed are selected. For example, the first page displays by default. If you do not browse to the other pages, only the items on the first page are selected. If you go to page 3 directly, then only the items on the first page and the third page are selected.

Support Considerations

Backup for a striped /mirrored volume is not supported if more than one extent of the volume resides on the same disk. For disk types supported, see Disks Supported by Arcserve UDP Agent (Windows) in the Arcserve UDP Agent (Windows) User Guide or online help.

The Arcserve UDP Agent (Windows) can only be managed by Arcserve UDP.

Miscellaneous Considerations

To mount a deduplicated NTFS volume, ensure that you mount it on a Windows Server 2012 system and that the deduplication feature is installed.

To browse the directory for restore destination, file copy source, copy recovery point destination, and mount recovery point location, the path limit is 255 characters.

To browse the directory for backup destination and file copy destination, the path limit is 156 characters.

After you rename a Microsoft Exchange database, reboot the Microsoft Exchange server. Otherwise, the Microsoft Exchange VSS writer does not update the database name and Arcserve UDP Agent (Windows) still displays the old database name.

The following tasks fail on Windows 2008 core and Windows 2008 R2 core machines:
- Mount recovery point
- File copy
- Catalog-less backup browse and search

To allow you to troubleshoot your computer problem effectively, Arcserve UDP Agent (Windows) does not work in the Windows Safe Mode.

To avoid a possible time sync error, if you change the system time when the browser is connected to the Arcserve UDP Agent service, close the browser and log in again.

After switching to the Arcserve UDP Recovery Point View and mounting a volume under the recovery point, if that recovery point is also included in a merge job, the merge job will fail. To avoid this problem, switch back to the Normal view for the merge job to succeed.

6.0 Issues Fixed

The following list identifies the fixes included in the current release of Arcserve UDP:

T245799
Hardlinks are restored as separate files.

T245802
MergeMgr.exe stops and shows the usage even though the command line is correct. This problem occurs when /BKDir <path> switch is specified and the <path> starts with \\ to describe the remote pathname (i.e.\\<hostname>\<pathname> ).

T245803
"Invalid email 'Recipients' address." pops up when clicking OK button in the Email Settings dialog for the Email Alerts. This problem occurs if the email address in the Recipients field contains a hyphen in its root domain name part. (ex. xxx@yyy.zzz-z)

T245807
This message is printed to the Console while MergeMgr.exe is running after being started manually. "WriteAttributeString: attr[DetailTime] value[<time string>] failed".

Note: This fix includes T245802 cumulatively. It resolves the following problem: MergeMgr.exe stops and shows the usage though the command line is correct.

T245826
The size of azure.log sometimes expands infinitely exceeding the configured max size in log4j-Azure.properties.

T245829 & T245831
In Cloud Configuration for copy job, "Test Connection" fails if the proxy server uses the BASIC method for authentication.

T245839 & T245849
Merge job fails at almost end of its task with error "Error: JobXXXXXXXX - Failed to delete file <path to the file>. Error code: -1". This problem does not occur on all machines, but usually occurs on some particular machines.

T245856
A blank screen displays in the browser when trying to open the Arcserve D2D Console after applying the r16.5 Update1 patch RO61712.

T245870
Boot kit wizard aborts without displaying any error when it is creating the boot image.

T2D2927 & T2D2928
VDDK 5.1 support.

T2D2930
The following error is shown randomly when attempting to save backup settings: "The operation has timed out. The maximum amount of time to complete the operation has been exceeded. Please try again later."

T2D2932
Merge job launched incorrectly when there are crashed sessions.

T2D2935
Exchange or SQL logs are not truncated daily even though the purge log option is set to purge daily.

T2D2939
Dump email item restore failed on the user when the user display name contains <> or other special characters.

T2D2944
Merge of recovery points fails when some disks have been merged completely.

T2D2945
Arcserve Backup merge jobs now complete successfully after Host-Based VM Backup sessions complete.

T2D2947
The virtual standby conversion job randomly fails. During a conversion job, the following error message is seen in Afcorfunction.log: "[Date Time 00 1608 3632 0X000004b3] CARCFlashDev::TryToAccess: Fail to AFConnectRemoteSource[\\networkshare\D2D\VM_xxxx]";

T2D2950 & T2D2954
Arcserve Central Host-Based VM Backup r16.5 backup will always perform a full backup even though an incremental backup was specified.

T2D2951
Merge job failed with not enough disk to be merged. This problem happens when there is a new disk added to the backup session during backup.

T2D2956
During restore process of an Exchange mail item, the From and Subject data are not being restored.

T2D2961 (RO58326)
When user set the File Copy Settings with Amazon S3 cloud destination, the bucket name on the cloud will have no prefix after the policy has been deployed to multiple machines, which can cause two different machines copying the data to the same bucket.

T2D2962 & T2D2966
Arcserve D2D r16.5 backups show as incremental even though a full backup does exist.

T2D2964
Arcserve D2D r16.5 Backup Exchange node job will crash on check if it is time to purge the transaction log.

T2D2971
A backup of some virtual machines via host-based backup, receive the following warning message: "Could not get volume information from virtualmachine guest OS". The result of this is that the catalog is not created for the VM, and thus file level restores are not possible.

T2D2978
Not all Exchange emails are displayed when expanding a recovery point after generating a Granular Restore catalog from a Arcserve D2D r16.5 backup of Exchange 2003 or Exchange 2007.

T2D2979 & T2D2982
Restore from the cloud shows a popup "Catalog data for the selected destination is not available. Click Sync to submit a catalog synchronization job". The time to perform this job takes long. This fix will use multithread to do the sync job which improves the performance.

T2D2987
Virtual standby conversion job failed with error "Failed in removing and adding disks for the virtual machine [VM_NAME]". This happens when the disk size is more than 1T.

T36A800
Backup job fails at the end of the job when trying to collect disaster recovery information.

T36A813 & T36A814
When user attempts to run pre flight check, the application returns error message: "Unable to retrieve information about the application. This can prevent application level backups from completing successfully."

T36A819
When user attempts to do a BMR on Windows XP SP3, recovery fails on C drive with the following error message in log file: "Get bootcode filename failed, resource id 65535."

T36A825
Running Arcserve D2D r16.5 SQL backup with purge transaction log option enabled, causes MS SQL databases recovery mode changing from simple to full after the backup.

T36A844 & T36A852
Cannot create a BMR ISO image with ADK 8.1.

T5E5181 (RO53672)
A Win2003 or WinXP machine may fail to boot after BMR. This usually happens when the BMR source machine has an OEM volume, and it's system volume and boot volume are not on the same volume.

T5E5182 ( RO53648 )
If merge job fails or crashes after finishing at least 10% in Arcserve D2D r16 Update7, user may continuously receive merge/backup/restore errors.

T5E5191
Backup job may crash with error 87 at the end of the job. This usually happens when backing up large amount of data to a NAS device.

T5E5192
Merge may fail with error 31 when recovery points reside on some NAS devices. This error can only be found when Arcserve D2D r16 Update7 is installed.

T5E5198
Merge may fail with error 31 when recovery points reside on some special NAS device.

T5E5203
Files under "BIN" folder will be deleted unexpectedly if check license fails in a copy recovery point job.

T5LE118
Arcserve D2D r16 backups will run a full backup each time, even though the backup schedule setting is hourly incremental backup when user change disk logical letter such as from D to E.

T5LE119
Backup job fails. The Arcserve UDP Agent (Windows) is unable to find the parent disk for backup after the merge.

T5LE120 & T5LE123
Arcserve D2D r16.5 backup failed with error=64. This happens when the network is not stable, and the agent write file fails.

T5LE121
Backup to NAS device fails randomly.

T5LE122
Backup to iOmega NAS device failed.

T5LE124
Arcserve D2D r16.5 backup job fails with error 80. This happens when an invalid file already exists on the destination.

T5LE125
Arcserve D2D r16.5 backup job can crash when starting.

T5LE130
Merge succeeds but the log displays 0 bytes of data will be merged.

T5LE133 & T5LE135
This fix corrects a security vulnerability (D2D web service getBackupVMList() is returning password fields in non-encrypted format) when using Arcserve D2D r16.5 backup sessions.

T5LE134
Arcserve D2D r16.5 web service crashes when setting the Exchange restore option on the GUI.

T5LE138
Arcserve D2D reports error 59 when running a backup job.

T5LE139
Arcserve D2D reports error 64 and error 59 when running Virtual Standby conversion.

T5LE141
Arcserve D2D r16.5 backup job crashes while collecting disaster recovery information.

T5TM103
In a BMR for a Windows server 2012 server with UEFI, the generated partitions have the different order as they are in source VM.

T5TM145
Unable to set Amazon cloud as the file copy destination, and information is not saved after clicking the Save button.

T55U009
Within the Arcserve Central Applications r16.5 Central Reporting Dashboard, some of the Email reports could show up as empty when executed with the filter set to last one day.

T55U010
SBS Server could freeze when Arcserve D2D r16.5 generates the Exchange Granular Restore Catalog.

T55U012 & R066936
Windows 2012 R2 support for Arcserve D2D and Arcserve Central Applications.

T55U015
Unable to open Arcserve D2D r16.5 from the tray icon and no error displays. The monitor will not open when there is not enough storage available to process the command.

T55Z001
Virtual Standby Conversion job failed to create a bootable snapshot for standby VM, when merge of snapshots of standby VM in HyperV runs long enough at the same time.

T55Z002
Last Successful Event for Copy Recovery Point job in the Arcserve D2D r16.5 Home Page under Protection Summary does not get updated even when it completes successfully.

T55Z004 & RO65682
Support vCenter Appliance in host-based agentless backup and virtual standby.

T55Z006
Support VMware VIX 1.12, 1.13

T55Z007
Arcserve D2D merge backup session fails with the following error:"[CMergeUtil::GetBackupInfo] Failed to read backupinfo.xml. (Path=[\\xxxxx})".

The backupinfo.xml file has an extra null character at the end, and the xml API is unable to process the file.

T55Z009
Arcserve Central Applications Reporting scheduled reports are incorrectly sent (time sent) when DST is in effect.

For example, A report is scheduled to be sent at 9:00AM, after DST change, it will be sent at 10:00AM instead.

T55Z010
Arcserve D2D r16.5 backup fails with the following error to iOmega NAS device "Error: Job00000xxx - Operations

(create, close,read, write) on file \\xx.xx.xx.xx\machinename\VStore\S0000000001\disk2

754413731.D2D.idx failed, Error code:5,[Access is denied]."

T55Z011
“A total of xxxMB unique data will be merged.” Message is not output on the Italian OS during merge job, which causes the merge process to hang.

T55Z017 & RO68016
VDDK 5.5 support and VIX 1.1.3 support.

T55Z019
Arcserve D2D merge will fail whe the backup sessions have no compression, no encryption and integrating Arcserve Backup with Arcserve D2D.

T55Z021
Protection Summary Total Size for file copy are recorded with uncompressed size, not the compressed size stored on cloud on Arcserve D2D.

T55Z022
Failed to restore Exchange database to rsg, when the file is such as [x:\mountpoint\mountpoint\LOGS3], x:\mountpoint\ is a mount point to external storage. The error [The system cannot find the path specified.]) will be shown.

T55Z023
Message "Failed to open file[Z:\filename.doc] error[3]" is written to the log file VMIMAGE.log even though the file is restored successfully.

7.0 Known Issues

The following issues are known to exist in this release:

Arcserve UDP Recovery Point View Related

After switching to Arcserve UDP Recovery Point View, the volume that is mounted under a file path in the backup session cannot be mounted.
Symptom

If the volume is still mounted, Arcserve UDP Recovery Point View directly opens the volume which is mounted by the operating system, not the backup session.
- If the volume is dismounted, nothing is displayed in Arcserve UDP Recovery Point View under that file path.
Solution

Use Mount Recovery Point to mount this kind of volume.

Arcserve UDP Agent (Linux) Related

If you open Arcserve UDP Agent (Linux) in Google Chrome, then the rows in the job status tab do not align with the corresponding column header.

In Red Hat Enterprise Virtualization, PXE-BMR in a DHCP environment does not work.

Encrypted volume is not supported. You cannot back up an encrypted volume.

FakeRAID is not supported for BMR. If your backup node is RHEL 6.4 and later, or CentOS 6.4 and later, or Oracle Linux Server 6.4 and later and the backup node includes Linux Software RAID, then you must use the CentOS-based Live CD to perform a BMR from such recovery points.

When you restore files from RHEL 5.x or CentOS 5.x recovery points using RHEL 6.x or CentOS 6.x D2D Server, some SELinux (Security-Enhanced Linux) attributes may not get restored.

When you download the two installation package files to a local folder, the full path of this local folder must not contain any special characters except blank spaces and the path should only include the following characters: a-z, A-Z, 0-9, - and _.

If you submit a File-level restore job or a BMR job using Local as the backup destination and then if you want to modify the backup destination to NFS share or CIFS share, you must first add the NFS share or CIFS share to the backup storage. After adding the NFS share or CIFS share, open the Restore Wizard and select the NFS share or CIFS share from the Session Location drop-down list, and then submit the job again.

Only the Red Hat compatible kernel is supported with Oracle Linux. You must select the Red Hat compatible kernel as the default boot kernel. The Oracle Unbreakable kernel is not supported and it should not be the default boot kernel.

If your backup node is a SUSE Linux Enterprise Server, then Arcserve UDP Agent (Linux) does not support performing a BMR in the Red Hat Enterprise Virtualization platform.

If you boot a PVM in the Citrix XenServer 6.x using a Live CD, the Arcserve UDP Agent (Linux) Backup Server is not available in the Live CD.

Backup Related

Backup or restore may fail when operating a VSS. Event ID 10006, 1503. or 6287 may display in the Windows Event log.
Symptom

The following messages can be found in the event log: "Illegal operation attempted on a registry key that has been marked for deletion" or "Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards."

Solution

For cause and solution, see the Microsoft KB article 2287297.

Mounting a volume fails and the message "Failed to mount recovery point to path: "Z:" . Incorrect function." appears.
Symptom

Mounting a session to a driver letter fails.

This happens when the destination is a local folder and on a FAT32 volume. Mounting a driver only supports creating the cache file on NTFS volume.

Solution

Add a new registry key and customize the cache file path to a different volume.

Follow these steps:
1. Create the key "AFStorHBAMgmt" on HKEY_LOCAL_MACHINE\SOFTWARE\CA\arcserve Unified Data Protection\Engine.
2. Create the string value "CacheFilePath".
More Information:

The cache file will be created by mounting a driver when a writable volume is mounted. For Granular Restore catalog/restore job, a writable volume is created. If the session is to back up volumes on Windows 8, Windows 2012, or a later operating system, always mount a writable volume when you mount a session to a driver letter.

You cannot mount a session to a 4 KB disk.
Symptom

From a server where the operating system is installed on a native 4 KB hard disk, mounting a recovery point fails with error "Failed to mount recovery point to path. Incorrect function."

Solution

Mount the recovery point from another server where the operating system is not installed on a native 4 KB hard disk.

When you submit a backup job from the Arcserve UDP Agent (Windows) UI, the backup job may not launch when the backup destination is using a data store on a Recovery Point Server.
Symptom

The backup submitted does successfully show, but from the Arcserve UDP Agent (Windows) UI, you cannot see any job monitor. This is because the backup job meets the maximum concurrent node count setting in the data store. The backup job is put into the waiting queue.

Solution

Open the Arcserve UDP Console UI, and the pending job monitor will show on the node view.

Backup is slow after extending a volume.
Symptom

The backup is sometimes slow if the volume which the destination is located on is extended. The filter driver that updates the tracking bitmap into the file periodically occupies the disk IO.

Solution

Offline and online the extended volume by disk manger or using the diskpart command. If the volume cannot be turned offline, reboot the machine.

If the Arcserve UDP Agent (Windows) machine is rebooted when a backup job is running, the job will be marked as "crashed" on the Arcserve UDP Agent (Windows) home page, but on the Arcserve UDP Console there is no job history for this job. This is because the job history item is sent to the Arcserve UDP Console at the end of the job but in case of reboot, there is no chance to send the job history from the agent to the server.

The Host-Based Agentless Verify backup job’s Compression Percentage on the job monitor is not correct.
Symptom

When a Host-Based Agentless Verify backup job is running, and if compression has been enabled in the plan, the Compression Percentage displayed on the job monitor is higher than the actual percentage.

All other backup jobs do not have this problem, including Agent backup jobs and Host-Based Agentless Full/Incremental backup jobs.

Solution

The compression percentage printed in the activity log is correct. Refer to it after the Host-Based Agentless Verify backup job is completed.

Instant VM Related

If a recovery point has mirrored system volume and you create a Instant VM using that recovery point, you may get some errors such as a Black Screen of Death.

BMR Related

Create boot kit failed with the following error:
"Failed to integrate the language package into the BMR ISO Image".

Symptom

This issue is caused by the third-party anti-virus software (McAfee) filter driver, but it can also happen with other third-party filters.

Solution

Disable your anti-virus software and try the boot kit creation again.

Unable to boot the server after performing a BMR.
Symptom

When the source machine is an Active Directory server performing a BMR to a physical machine with different hardware or to a virtual machine on a Hyper-V server, the server does not boot and a blue screen displays with the following message:

STOP: c00002e2 Directory Services could not start because of the following error: a device attached to the system is not functioning. Error status: 0xc0000001.

Solution

Reboot the system to the BMR PE environment, rename all *.log files in the C:\Windows\NTDS folder, and restart the system. For example, rename the file edb.log to edb.log.old and restart the system.

Unable to map the source disk to the destination disk during BMR even though the size of both disks is exactly the same.
Symptom

You may be unable to map the disk/volume during BMR, when the target machine is a VM with IDE disk on a 2008 Hyper-V server or a 2008R2 Hyper-V server.

If you restore data to a VM with IDE disk on a 2008 Hyper-V server or a 2008R2 Hyper-V server using BMR, it will not able to map the source disk/volume to the target disk/volume, even though the sizes of both disks appear to be the same. This is because that when you create an IDE disk on a 2008 Hyper-V server or a 2008R2 Hyper-V server, the actual disk size is smaller than the size that you specified.

Solution

Create a bigger disk on the VM. For example, if you want to restore data from a 25 GB disk, it is suggested to create a 26 GB disk on the target VM.

If you use Windows ADK 8.1 to create a BMR ISO, after you boot the machine up using this ISO, you may find that there is no disk detected in the PE system.
Symptom

This is observed on VMWare ESX Server. For Windows 2003 VMs the default disk controller is LSI Logic SCSI adapter and the driver for this type of SCSI adapter is not included in Windows ADK 8.1. You may also observe this on some old servers with old SCSI adapters.

Solution

To solve this problem, obtain the drivers from the hardware vendor web site and load the driver from the BMR user interface.

File Copy Related

File copy processing data is dependent on the catalog job. So, if a catalog job is generated for a scheduled file copy job before its first or earlier file copy job is finished, then when the actual scheduled file copy job is running, the job monitor for processing the data is incorrectly displayed.
Symptom

The catalog for a future file copy job is generated before its first file copy job is finished.

Solution

Ignore the incorrectly displayed data shown being processed in the job monitor.

Host-Based VM Backup Related

When you perform Incremental backup jobs for VMware virtual machines, the backed up data size of the Incremental backup jobs may be larger than expected.
Symptom

This is a known VMware issue where it involves Changed Block Tracking (CBT).

Solution

To correct this behavior, set the following registry on the proxy server:

[HKEY_LOCAL_MACHINE\SOFTWARE\CA\arcserve Unified Data Protection\AFBackupDll\<VM instance UUID>]

"ResetCBT"=dword:00000001

Example:

[HKEY_LOCAL_MACHINE\SOFTWARE\CA\arcserve Unified Data Protection\AFBackupDll\502d3c43-e3c9-9919-78f9-89082ca5e1cc]

"ResetCBT"=dword:00000001

Note: After the registry value is set, the next Incremental backup job converts to a Verify backup job and then the subsequent Incremental backup jobs continue to run with the appropriate size.

Due to a VMware known issue, when the storage DRS is enabled and the storage vMotion occurs while the backup job is in progress; the backup job can fail. The activity log specifies the following message: "Unable to open the VMDK file." VMware reported the following error: "A file was not found."
For more information, see the VMware KB Article 2055943.

The recovery of a VM with VMDK larger than 2-TB of disk fails because the VM failed to create a snapshot.
Symptom

The backup source VM has VMDKs larger than 2-TB and the ESX/ESX(i) server with a version lower than 5.5 can only support a virtual disk of up to 2-TB disk in size. However, during the VM recovery, the following errors can occur:
- In the vSphere Client:
  - "Create virtual machine snapshot VIRTUALMACHINE File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>'".
  - "File is larger than the maximum size supported by datastore".
- In the hostd log file for ESX/ESXi 4.x:
  - "Snapshot guest failed: The file is too big for the file system."
- In the hostd log file for ESXi 5.0/5.1:
  - "Failed to do snapshot op: Error: (21) The file is too big for the datastore."
Solution

This is a VMware limitation. The maximum size that VMware ESX/ESX(i) server version lower than 5.5 supports is 2 T-16 GB, which is equal to 2032 GB.

It is recommended to use VMware ESX(i) server 5.5 as the destination to perform conversion with a large disk.

For more information, see the VMware KB Article 1012384.

Creating a snapshot fails when more than seven disks are attached to a single SCSI controller for a Windows VM running on an ESXi server.
Symptom

When you run a backup job on a virtual machine containing a SCSI controller with more than 7 VMDKs, the backup job fails. The reason why the backup job fails is because VMware requires a maximum number of free slots for VMDKs on a particular SCSI controller to create a snapshot. A SCSI controller can have a maximum number of 15 slots. For example, if a SCSI controller has 7 VMDKs, a snapshot can be created for each VMDK. (A total of 14 slots are used with one slot free.) If a SCSI controller has 8 VMDKs; the backup job fails because the snapshot cannot be created due to only 15 available slots.

Note: Manually creating a snapshot also fails.

Solution

For virtual machines with more than seven disks on a single SCSI controller, perform the following steps:
1. Shut down the virtual machine.
2. Create more thin virtual disks which allow you to add more SCSI controllers.
3. Distribute the existing disks between multiple SCSI controllers.
4. Power on the virtual machine.
Snapshots can now be created for each VMDK.

This issue is a VMware limitation where Arcserve Backup can only support the number of VMDK disks for backups.

For more details, see the following VMware Knowledge Base article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2015181

When you import VMware virtual machines from vCenter Server/ESXi 5.0 Update 3 and above while using HTTP protocol and port 80, the connection fails.
This is a known issue with VMware. For your reference, you can review the knowledge base article here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2069149

When a VM is imported from a Hyper-V server, the VM becomes disabled after the Host-Based Agentless Hyper-V VM restore job overwrites the VM. The reason why this occurs is because the instance GUID of the restored VM is different from the original instance GUID; which was imported from the Hyper-V server. The VM instance GUID cannot revert back to the original instance GUID.
To resolve this issue, remove the old VM from Central Protection Manager and import the new VM.

An ESX/ESXi/vSphere 5.5 purple screen of death appears when a Arcserve UDP job runs.
Symptom

This is a known VMware issue affecting ESXi 5.0, 5.1, and 5.5 hosts and virtual machines using the E1000 and E1000e virtual network adapters.

Solution

Switch to a VMXNET3 adapter. For more information, see the VMware KB Article 2059053.

During backup, the Arcserve UDP agent merges the child disks data to the corresponding parent disk and creates a single disk image. Therefore the parent-child relationship no longer exists after VM backup. As a result, only the parent disk is recovered and the "differencing disks" configuration is lost, however no data is lost. You can retrieve the data in a single merged disk after VM recovery.
This behavior is expected for agentless backup. You can configure the "Differencing disks" manually after a successful VM recovery.

Import VM fails when duplicate VM instance UUID exists.
Symptom

When a VM is imported to the node view, it fails if another VM with same VM instance UUID was already added to the node view.

A host-based VM backup plan is saved, it fails when the selected proxy machine is installed with Arcserve D2D r16.5.
Symptom

When a host-based VM backup plan includes a proxy machine that has the previous release of Arcserve D2D installed (for example, r16.5), the error message “Cannot find dispatch method” appears when the plan is saved.

Solution

This problem occurs because, the API of the current version is not compatible with the API of the previous version of Arcserve D2D. As a work around, you can manually upgrade Arcserve D2D to the current version of the Arcserve UDP Agent (Windows).

The host-based VM backup job may hang at the phase "Starting Backup" for a VM.
Symptom

The host-based VM backup job hangs for hours and cannot proceed.

Solution

End afbackend.exe according to the process ID in the activity log, remove the VM snapshot if any, and resubmit the backup job.

After performing a restore job for a host-based VM backup Hyper-V virtual machine (VM), the status of the disks, except the boot disks on the recovered virtual machine is Offline.
Symptom

The behavior of the operating system creates the offline state by default.

The SAN policy was introduced in Windows Server 2008 to protect shared disks that are accessed by multiple servers. The default SAN policy from the source VM is “Offline Shared” for all SAN disks except the boot disk. Setting the policy to Offline enables the SAN disks to be offline during startup. After recovery, a new disk for the VM is created. The disk file from the VM appears to be a SAN disk where the operating system sees it as being offline. When the offline disk is set to be back online, the disk remains online even after rebooting the system.

Solution

As a workaround, specify the DISKPART.exe command: SAN POLICY=OnlineAll setting for the source VM before backup. Because the disks can be shared among other servers, data corruption can occur. It is important that you use the correct SAN policy to protect the data.

DISKPART.EXE command line

Query SAN policy:

DISKPART > san

SAN Policy: Offline Shared

Change SAN policy:

DISKPART > san policy=OnlineAll

DISKPART successfully changes the SAN policy for the current operating system.

The iSCSI hard disk that is attached to a Hyper-V virtual machine will not be backed up.
Symptom

After backing up a Hyper-V VM, the volumes on iSCSI devices are not listed in the restore UI.

Solution

Create an agent-based backup plan in Arcserve UDP or use <cadp_agt_windows> to back up the virtual machine.

Pre/Post commands cannot be executed by host-based agentless backup jobs on a Hyper-V VM when the guest operating system is Windows Server 2003.
Symptom

For host-based agentless backup jobs for a Hyper-V VM, if the guest operating system is Windows Server 2003, the Pre/Post commands cannot be executed. The activity log prints the warning "The virtual machine name is not expected. Pre/Post commands cannot be executed".

Solution

Windows Server 2008, Windows Vista, or a later operating system do not have this problem and should be used.

Installation/Remote Deployment Related (Agent)

Install mounting driver failed with error code 1460 in the debug log.
Symptom

The Windows setup API reports error 1460, which means that the timeout period expired. The default timeout value is 300 seconds for updating the device driver.

Solution

To adjust the timeout value, follow these steps:
1. Type gpedit.msc in the Start Search box and press Enter.
2. Click Continue when the UAC prompt appears.
3. Navigate to the following policy location:
  Computer Configuration\Administrative Templates\System\Device Installation
4. Enable the following policy setting:
  Configure device installation timeout.
5. Specify a new timeout value in seconds.

Log View Related

The log filter does not work when the NodeName is VM (host name) and the log view is loaded by clicking the View Logs link.
Symptom

In the log view, if a protected VM does not have a hostname, then its NodeName value is displayed as "VM(node name)". In this case, other filters do not work.

Solution

You can manually modify the NodeName from VM (host name) to host name, and then all the filters will work fine. For example, modify NodeName "VM(xxxxx01-AB)" to "xxxxx01-AB".

Microsoft Exchange Related

Exchange database restore fails with error: "failed to mount it".
Symptom

This occurs when the Exchange server is installed inside a VM, and is running Arcserve UDP Agent (Windows) to protect this VM. After the backup runs for some time, if the VM is reverted back to a previously saved VM snapshot, and you try to recover the Exchange database to the original location, the restore fails with error "Exchange storage group/database [DB_Name] has been restored to its original location, but failed to mount it."

The root cause is still being investigated, but currently seems to be related to the time stamp recorded inside the Exchange database and the latest transaction log files.

Solution

Try to recover the Exchange database to an alternative directory, or dismount the database and remove all files in the destination folder before performing the restore.

Microsoft SQL Server Related

The Arcserve UDP Console may respond slowly if Microsoft SQL Server cannot allocate more memory.
Symptom

Microsoft SQL Server may need to allocate more memory to process the query, especially when there is lot of data in the Arcserve UDP database. But if Microsoft SQL Server cannot acquire memory due to the non-availability or maximum limit configured, then query processing will become very slow and therefore impact the Arcserve UDP Console responsiveness.

Solution

Delete some logs from the database using Log/Delete and restart the SQL Service.

Recovery Point Server (RPS)/Data Store Related

The antivirus software unexpectedly deletes the data store file.
Symptom

Backup or replication job fails with error “system cannot find the file specified”.

Check Windows Event log. McAfee detects the data store file (for example, P0000000042.data ) as Exploit-ScriptNull Trojan virus and deletes it.

Solution

Configure the antivirus setting to set the Recovery Point Server (RPS) Data Store location in the exclusion list.

Note: Some antivirus software requires you to set the exclusion list on the server side.

It may take up to several minutes to cancel a replication job when the destination is a deduplicated data store.
Symptom

This happens when you set the network throttling to a pretty low bandwidth or the network throughput to the destination RPS server is slow. Therefore, it may take several minutes to wait for the queued data to be sent.

Solution

Wait for the replication job to exit gracefully.

If the following two conditions exist, the hash memory for the data store is displayed incorrectly when modifying the data store:
- The memory of the RPS server is less than or equal to 4 GB.
- You do not select the maximum value for the hash memory when creating a data store.

Recovery Point Server (RPS)/Import from Hyper-V/Node Related

An 'Administrator privilege is required.' error can occur when trying to add a node by IP address or node name and prevents you from adding the node. A "Check if the account has administrator permission for this Hyper-V server" error can occur when trying to import from Hyper-V and prevents you from importing virtual machines.
Symptom

When you try to add a node by IP address or node name on Windows operating systems that support User Account Control (UAC), (Windows Vista or later versions), or try to import virtual machines from a Hyper-V server that support UAC, and you use a new Windows user account that is a local account in the administrators group but it is not the built-in administrator, the following message displays:

"Administrator privilege is required."

Solution

Use a built-in administrator or a domain administrator. Or, you can disable Remote UAC.

This is the default Windows behavior called UAC remote restrictions. If you still want to use this account to add the node, disable Remote UAC by performing the following steps:
1. Click Start, type regedit in the Search programs and files field, and then press Enter.
  The Windows Registry Editor opens.
  
  Note: You may need to provide administrative credentials to open Windows Registry Editor.
2. Locate and click the following registry key:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. From the Edit menu, click New and then click DWORD (32-bit) Value.
4. Specify LocalAccountTokenFilterPolicy as the name for the new entry and then press Enter.
5. Right-click LocalAccountTokenFilterPolicy and then click Modify.
6. Specify 1 in the Value data field and then click OK.
7. Exit the Registry Editor.
For more detailed information about Windows behaviors, see the article http://support.microsoft.com/kb/951016.

Unable to remove specified hypervisor for node.
Symptom

Removing the hypervisor function for a node is not provided in this release.

Solution

Remove the node and add it again.

There is no warning or pop-up message when you try to add a node to a console, which is already being managed by another console.
Symptom

With the all-in-one UI in Arcserve UDP, it is not expected that users will have multiple Arcserve UDP Consoles and therefore the scenario of moving the agent from one server to another will only happen when the old server is retired.

Solution

Moving the node from one console to another is a very rare scenario.

Registry Related

If the backup destination is a deduplicated-enabled NTFS volume on Windows Server 2012 and Arcserve UDP Agent (Windows) is installed on Windows 2003, restore, merge, or catalog jobs can fail. The job fails with Windows error code 50 and message "The request is not supported".
Symptom

McAfee or another third party software set EnableECP=1 in the registry when they are installed on Windows Server 2012.

Solution

In the registry, change the value of EnableECP from 1 to 0 under the following key:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanManServer\Parameters
```
For more information, see http://support.microsoft.com/kb/2817216.

Replication Related

Aborting the RPSReplication.exe process at the replication source side may cause the second replication job to fail.
Symptom

The second replication job will hang in the Prepare status and fail after 10 minutes.

Solution

You do not need to perform any specific operation. After the second replication job fails, the makeup job will be triggered.

Restore Related

Restoring files to an alternate location which is a remote share folder fails with error message "Access is denied." in the activity log.
Symptom

When the restore destination is a remote share folder such as \\FileServer\ShareFolder\RestDest, and the backup destination is a remote share folder with the same path, such as \\FileServer\ShareFolder\RestDest, the error occurs.

If the user account which is used to connect to the root share folder is not in the permission list, the restore job will fail no matter what account is used for the restore destination folder.

Solution

Add the user account which is assigned for the backup destination to build the connection into the permission list of the root share folder and ensure the user account has proper permissions to restore the file.

Add the user account into the Backup Operators group and ensure it has the permission to override security restrictions.

After you have upgraded the operating system, you may need to re-enter the encryption password or session password when restoring a file from Arcserve UDP Agent (Windows).
Symptom

If encryption is enabled for the recovery point, you do not have to enter the password for recovery points backed up from the current server. However, if you upgrade the Windows OS (For example, from Windows 2008 to Windows 2008 R2), the passwords will not be automatically filled in on the Arcserve UDP Agent (Windows) user interface and you must re-enter the password.

Solution

Record the recovery point encryption password or session password and keep it in a safe place for retrieval.

Browsing a volume fails and the message "Failed to browse this volume: Incorrect function." appears. This happens with both, Browse Recovery Points and Find Files/folders to Restore options for catalogless backup.

A Microsoft Exchange Granular Restore catalog job is reported as successful but no catalog is generated.
Symptom

When generating an Exchange Granular Restore catalog file, if the Arcserve UDP deduplication service is terminated or the remote share folder can not be accessed, the Granular Restore will treat the related database tables as if they do not exist in the current database. The catalog file will include part of the Exchange items.

Solution
1. Open the catalog folder, and enter the child folder of GRT_x (x is a number, standing for the sub session).
2. Delete all the files ,except GRT_x.xml.
3. Open GRT_x.xml, and modify the item IsCreated to "0".
4. Save the GRT_x.xml.
5. Submit an on-demand Granular Restore catalog job.

Server Connection Related

Server connection error is displayed when browsing the logs.
Symptom

When you browse the activity logs from the Agent or the Console, the following error might be displayed:

Failed to connect to server 'arcservedocs.com'.

Solution

You can just ignore this message.

Virtual Standby Related

The disks start in an offline status when powered on. This behavior occurs because SAN policies were introduced to Windows 2008 and later operating systems. The operating system protects shared disks that are accessed by more than one server. The first time the server detects the disk, Windows places the disk in an offline state. After the disk is placed in an online state, the disk remains in an online state.
Another cause for this behavior relates powering on virtual machines that contain "read only" volumes. To correct this condition, place the volumes on the disk in a writable state.

The application does not support importing vCenter servers using VMware Linked mode. To protect all vCenter server instances in Linked Mode groups, add each vCenter server instance individually.

Virtual standby does not support converting recovery points to Hyper-V format when the system volume or the boot volume on the source computer resides on dynamic disks.

Virtual standby does not support creating virtual standby tasks that let you define the quantity of dynamic RAM used by the virtual machines that you are protecting on Windows 2008 R2 SP1 and Windows 2012 Hyper-V Server systems.

Virtual standby does not support performing V2P recoveries from the current state for the nodes that were protected by a Host-Based VM Backup in a powered on state. Instead you can use any snapshot other than the current state.

Virtual standby does not support performing V2P recoveries on nodes that were protected by Host-Based VM Backup in a powered off state. To perform a full VM recovery, submit a Recover VM job using Host-Based VM Backup.

When you perform a V2P recovery using the current snapshot, a message may appear that indicates the following:
Failed to get Recovery Point information.

This behavior occurs when you perform a V2P recovery using the latest snapshot and a conversion job for the node did not complete after the virtual standby task was redeployed to the node.

Solution
1. Submit a Arcserve UDP Agent backup job to capture the current state of the node. Then perform a Bare Metal Recovery of the node.
2. Power off the virtual standby virtual machine and then submit a virtual standby conversion job to create a current recovery point snapshot for the node.

The V2P user interface may not display the latest snapshot. This behavior occurs when you perform a V2P recovery after you complete a V2P recovery from the latest snapshot.
Solution

Perform the V2P recovery using Arcserve UDP Agent Bare Metal Recovery.

When the backup source machine (where the Arcserve UDP Agent is installed) contains native 4KB sector disks and the Arcserve UDP Agent backup job backed up the volumes on the 4KB sector disks, the standby virtual machine that converted the Arcserve UDP Agent backup sessions cannot detect the partitions and volumes of the corresponding 4KB sector disks. You can expect this behavior when the source disks contain 4KB sectors and the standby virtual machine supports 512B sector disks. After conversion, the guest operating system on the standby virtual machine fails to locate the disk metadata due to the sector size changes.
Note: This limitation applies to only virtual standby jobs running on Hyper-V servers.

For a host-based virtual machine session, if there were network adapters attached to the VM and later the adapters were detached, there will be more network adapters listed in virtual standby than the current list in the VM.

The conversion of a 2-TB disk file fails because the VM failed to create a snapshot.
Symptom

The Arcserve UDP Agent (Windows) has a disk of 2-TB and the ESX/ESX(i) server with a version lower than 5.5 can only support a virtual disk of up to 2-TB disk in size. However, during the conversion, the following errors can occur:
- In the vSphere Client:
  - "Create virtual machine snapshot VIRTUALMACHINE File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>'".
  - "File is larger than the maximum size supported by datastore".
- In the hostd log file for ESX/ESXi 4.x:
  - "Snapshot guest failed: The file is too big for the file system."
- In the hostd log file for ESXi 5.0/5.1:
  - "Failed to do snapshot op: Error: (21) The file is too big for the datastore."
Solution

This is a VMware limitation. The maximum size that VMware ESX/ESX(i) server version lower than 5.5 supports is 2 T-16 GB, which is equal to 2032 GB.

It is recommended to use VMware ESX(i) server 5.5 as the destination to perform conversion with a large disk.

For more information, see the VMware KB Article 1012384.

After changing the password of Virtual Standby monitor and updating the node for Virtual Standby monitor in the Arcserve UDP Console UI, the deployment for the plan that has used that monitor server can fail.
Symptom

Deploying the plan failed and the following error message displays: "Unable to apply 'Virtual Standby settings' to node 'xxx'. (Failed to connect from xxx to the monitor: xxx. Invalid user credentials)".

Solution

Edit the Virtual Standby task in the plan, enter the correct password for the monitor, and save the plan.

The custom static IP address is not activated in the standby VM.
Symptom

If you customize the static IP address in Arcserve UDPand then start the standby VM, sometimes the static IP address is not activated in Windows although it is set in the network adapter successfully. When you execute the command line ipconfig in the standby VM, it shows a random IP address, while the IP setting in the TCP/IP property dialog of the network adapter is correct.

This happens when the source machine (product server) had the same static IP setting as the one set for the standby VM. Windows keeps all IP settings of all network adapters in the registry. When the standby VM starts, the legacy IP setting is still checked althought its corresponding network adapter (belonging to the product server) is absent. If Windows finds any legacy static IP address is assigned to a new network adapter, a dialog displays asking you to confirm.

Solution

To activate the new IP address, open the TCP/IP properties dialog of the specified network adapter, check whether the IP setting is correct, and then click OK and follow the steps of Windows to re-set it manually.

VSS Snapshot Related

Due to a VSS snapshot problem caused by VMware or Microsoft inside the VM guest OS, catalog generation for agentless backup of VMware VMs may fail with the following message: "Failed to map an index block to the correct volume block. An IndexAlloc Error has occurred."
Workaround
1. Run 'chkdsk' to ensure data consistency inside the guest OS.
2. Power off the VM so that the VSS snapshot inside the guest will not take place.
3. Back up the VM in a powered off state.
Note: This problem occurs rarely. For more information, see the VMware KB Article 2006849 or the Microsoft KB Article 2853247.

8.0 Compatibility Issues with Arcserve UDP Agent (Linux)

Consider the following third-party software limitations that can affect the performance of Arcserve UDP Agent (Linux):

The non-server edition Windows share cannot be used as a backup destination.

The backup job fails if the backup destination is an NFS server version 4 and the host name of the NFS server is not registered to DNS.
Symptom

You have provided an NFS server version 4 as your backup destination and the host name of the NFS server is not registered to DNS. When you run the backup job, the backup job fails.

Solution

Register the host name to DNS.

PXE boot fails on Red Hat Enterprise Virtualization (RHEV) and Citrix Xen virtual machine (VM). To avoid this problem, upgrade to gpxe version 1.0.1.

Some versions of Data Domain NAS do not support the file locking mechanism of NFS. Such NFS shares cannot be used as a backup destination.
Symptom

You have provided some version of Data Domain NAS using NFS as your backup destination. When you are performing a backup to that backup destination, the backup fails. The reason is that some versions of Data Domain NAS do not support the file locking mechanism of NFS. Such NFS shares cannot be used as a backup destination.

Solution

To avoid this problem, use CIFS as your backup destination. If the backup job still fails when you provide CIFS as the backup destination, follow these steps:
1. On the node that you want to back up, ensure no CIFS share is mounted.
2. Open the Command Prompt window on the node and enter the following command:
```
 echo "0"  >  /proc/fs/cifs/LinuxExtensionsEnabled
```
You can now submit the backup job for the node.

When you back up the RHEL 5.1 node, the setroubleshoot system service uses the system memory for the backup process.
Symptom

When you back up the RHEL 5.1 node, the setroubleshoot system service uses the system memory for the backup process. If you perform multiple backup jobs, the setroubleshoot service generates multiple alerts in the /var/log/messages file and it uses all the system memory. After many backups, the backup node memory is full and it does not have any free memory.

Solution

To avoid this problem, stop the setroubleshoot system service on the backup node using the following command:
```
service setroubleshoot stop
```

9.0 Limitations

The following limitations are known to exist in this release:

Arcserve UDP Agent (Linux) Related

When managing Arcserve UDP Agent (Linux) using the Arcserve UDP user interface, the following tasks are not supported:
- Exclude volumes for individual nodes.
  Note: You can use global volume filters which apply to all nodes in a plan.
- Simple backup schedule.
  Note: You can use advanced backup schedule.
- Discover a node using a script.
- Backup storage management and alerts.
- Recovery set management on the backup server side.
  Note: You can still use recovery set management on the client side.
- Command line "d2djob --delete" and "d2djob --export".

LVM (Logical Volume Manager) is not supported on SUSE Linux Enterprise Server (SLES) 10, but is supported on SLES 10 SP1 to SP4.

Backup Related

File Backup Limitations:
X64 - up to 370 million files

X86 - up to 110 million files

Note: For X86 users, if you have more than 110 million files to back up, use an X64 computer or you can refer to the troubleshooting topic "Catalog Job fails when backing up a large number of files on Windows 2003 X86 machine" for an alternate solution.

If the Arcserve UDP Agent (Windows) could not resolve the hostname of the Arcserve UDP Console server or the RPS server, or the RPS server could not resolve the hostname of the Arcserve UDP Consoler server, the backup job could not be submitted. The workaround is to configure the DNS server or add entries in the hosts file to verify the hostname could be resolved correctly.

BMR Related

If you are attempting to perform a BMR on a Generation 2 VM of Hyper-V 2012 r2 Server, create the BMR ISO using Windows ADK 8.1. Using Windows ADK 8 or Windows AIK to create the BMR ISO causes failure to accept input or failure for the BMR to start.

Catalog Related

If you are attempting to generate an Exchange Granular Restore catalog, you may get a return error (-1019 or -1035), indicating that the catalog is generated successfully, but no catalog is actually generated. This may be because the destination cannot be accessed and the related database tables will be treated as if they do not exist in the current database. The catalog file will then only inlcude part of the Exchange items.

Copy Recovery Point Related

Copy recovery point does not support copy to a data store with or without deduplication enabled. You can only copy a recovery point to a local/share folder.

Dashboard Related

Dashboard supports grouping jobs in a specified category and displaying detailed job information for all kinds of jobs except for a BMR job.

The destination information which displays in the dashboard job detail table indicates the destination of the corresponding tasks which are configured in the plan at the time the job is being executed.

For on demand jobs that are manually submitted from the Arcserve UDP Agent (Windows) user interface, for example, restore job, copy recovery point job, the corresponding plan name is displayed as N/A in the Dashboard. The job destination information is not shown in the Dashboard detail information pane. However, the job destination information for on demand catalog jobs are displayed in the Dashboard detail information pane under certain conditions.

Data Store Related

When deleting an unknown data store and adding it again, the UI may indicate "This name is already being used by another data store on the server. Please specify a different data store name."

File Attribute Related

The Arcserve UDP Agent (Windows) requires the file attribute "system" to convert the backup destination folder to the Arcserve UDP Recovery Point View. However, on some NAS filers, the file attribute "system" is not supported, therefore you cannot change the destination to the Arcserve UDP Recovery Point View.

High Availability Related

Do not use multiple Arcserve UDP user interfaces to manage the same Arcserve Replication and High Availability control service. It will cause reports to be missing.

Host-Based VM Backup Related

When IDE or SATA disks are installed on the guest operating system (OS), the backed up OS file becomes inconsistent. As a result, if you recover the backed up data then the recovered OS becomes unstable or stops working. This issue can also cause unpredictable problems with host-based VM backup. For example, the volume letter is not displayed.

When running multiple VMware backups simultaneously with transport mode as HOTADD, tthe backup job crashes. To resolve this, set the registry key VDDKEnforceTransport to nbd in the host-based backup proxy machine.

When importing a VM from VCenter 5.5, and you select "HTTP" protocol to connect the VCenter, the VM infrastructure tree does not display any nodes.

For a Hyper-V VM which has the application (SQL Server or Exchange) installed, host-based VM Backup supports application consistent backup and restore at the VM level. However, SQL Server and Exchange DB/Mailbox level recovery is not supported. This is different with VMware VM.

Restoring a Hyper-V virtual machine to an earlier version of the target Hyper-V server is not officially supported. Nevertheless, you can still continue to restore it. However, it is not guaranteed that the restored virtual machine will have full functionality due to the Hyper-V server compatibility.

Arcserve UDP does not support the backup and restore operations of Hyper-V agentless VMs using SR-IOV.

Anytime the hypervisor of the VM changes for either of the following reasons, if Arcserve UDP has the new hypervisor connection information already, the VM will be detected under the new hypervisor after the Update VM information is triggered.
- The VM is moved to a different hypervisor (and retained VM Instance UUID).
- The hypervisor hostname/IP is changed.
Once that happens, you will have to redeploy the plan to the VM to continue backups.

A virtual machine cannot be protected by the Host-based agentless plan which uses itself as a backup proxy.

Plan/Task Related

You cannot delete multiple plans at the same time.

Report Related

In IE8, the report chart does not display.
Solution

To resolve this, perform one of the following tasks:
- Add this site into the IE8 trusted site list.
- Enable "Binary and script behavior" in Security settings.

Restore Related

When small files are restored (approximately 100 bytes), on volumes with 32 KB or 64 KB cluster size, the file content is different with the source data.

The following limitation exists for catalog-less sessions:
For some file attributes, if the restore destination is not supported, the restore job will fail. For example, some files have a security attribute, but only Windows NTFS is supported. If you restore it into a SAN, the restore job will fail.

Restoring EFS (Encrypting File System) files to an alternate location fails with error "Access is denied".
For catalog-less restores, you cannot restore EFS files, which is a limitation of the EFS feature.

For more infomation see, the Microsoft Article 700811.

Virtual Standby Related

In VMware ESX Server environments that are configured in a storage area network (SAN), the application copies only the first, full backup session to the ESX Server system using the SAN. For all subsequent full and incremental backups, the application copies the converted backup sessions using the LAN. The application behaves in this manner due to a VMware limitation. For more information, see the VMware website.

Due to a VMware limitation, virtual standby cannot create virtual machines on ESXi Server systems using a free license. To create virtual machines, a purchased license is required.

Due to a known VMware limitation, errors in the Activity Log appear in English when the Location is set to a non-English locale.

Due to a VDDK API limitation which prevents the mounting of GPT volumes, virtual standby cannot support the UEFI (Unified Extensible Firmware Interface) system, therefore when you deploy a virtual standby task whose standby destination is VMware vCenter/ESX(i) server to a UEFI system, deployment fails.

Due to a Hyper-V limitation which does not support a virtual machine that uses the Unified Extensible Firmware Interface (UEFI), virtual standby cannot support the UEFI system. Therefore when you deploy a virtual standby task whose standby destination is Hyper-V server to a UEFI system, deployment fails. This is applicable when the Hyper-V server is 2008, 2008 r2 or 2012.
If the destination Hyper-V server is 2012 r2 and the source node is a UEFI system, and is one of the following operating systems, it will be supported:
- Windows Server 2012
- Windows Server 2012 R2
- 64-bit versions of Windows 8
- 64-bit versions of Windows 8.1

Miscellaneous Related

The interactions between the scenario properties are implemented (such as the rewind option with scheduled bookmarks). You can set the relative properties manually.

Editing root directories of the full system Linux scenario is not supported.

The Arcserve UDP solution does not support the Arcserve UDP Agent (Windows) integration scenario and the host-based VM backup integration scenario created from Arcserve Replication and High Availability.

When the Arcserve UDP Server, Agent, or Recovery Point Server is running on machines with Intel 82574L network adapter or E1000e vNIC in virtual machines from VMware, the TCP Segmentation Offload (TSO) will be disabled when starting the Arcserve UDP Agent Service. This is because a data corruption problem may occur on such environments when TSO is enabled. You can also manually disable TSO or replace with another kind of network adapter to avoid this problem.
For more information about this problem, see "Errata 17 - Tx Data Corruption When Using TCP Segmentation Offload" in the following Intel document:

Intel 82574 Family Gigabit Ethernet Controller Specification Update

The Recent Events panel in the Arcserve UDP Console is not automatically refreshed after jobs are completed; the panel must be manually refreshed.

Considering that there might be hundreds of data stores that are managed and used simultaneously on the same Arcserve UDP Console, the center pane of the RPS node page is refreshed every 15 minutes. The delay is to avoid high load while refreshing. Therefore, the most recent usage statistics values for the data stores might be delayed by 15 minutes.

If you select Microsoft SQL Server 2008 R2 Express as the database, Setup will always install the English version of Microsoft SQL Server 2008 R2 Express. If you want to use other languages for the Microsoft SQL Server 2008 R2 Express database, download and install it, and then run Setup. The link to download Microsoft SQL Server 2008 R2 Express is:
- English: http://www.microsoft.com/en-au/download/details.aspx?id=30438.
- Japanese: http://www.microsoft.com/ja-jp/download/details.aspx?id=30438.
Note: After installation, SQLE will always create English menus in the START menu item even if other SQLE languages have been installed.

10.0 Language Support

Documentation is available in English as well as multiple local languages.

A translated product (sometimes referred to as a localized product) includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

This release is available in the following languages:

English

Chinese (Simplified)

Chinese (Traditional)

French

German

Italian

Japanese

Portuguese (Brazil)

Spanish

11.0 Acknowledgements

The following license agreements for Arcserve UDP Console, Arcserve UDP Recovery Point Server, and Arcserve UDP Agent (Windows) are available in the \Bookshelf_Files\TPSA folder in the Arcserve Unified Data Protection Knowledge Center:

Apache HTTP Web Server 2.2.21

Apache Software License v.2.0
- AWS SDK for Java 1.3
- Axis 1.4
- Axis2 1.4.1
- Axis2/C 1.6
- Derby 10.6.2.1
- GWT 2.4
- Log4j 1.2.15
- Quartz 1.6.5

ATL Server Library and Tools 9.0.70425 Alpha

bind 9.6.1-P1

Eclipse Public License v.1.0
- Eclipse Equinox AspectJ r.1.6.9
- Eclipse Equinox AspectJ r.1.8.5

FusionCharts Free 2.2

Jackson 1.9.2

jaxws 2.2.7

Jersey 1.17.1

JSW (Java Service Wrapper) 3.2.3

lzjb 2009.06

OpenSSL 1.0.1e

Oracle (formerly Sun) JRE 1.7.0_51

Oracle (formerly Sun) JRE 1.8 update 45

SQLite 3.7.17

Tomcat 7.0.29

VMware Virtual Disk Development Kit 5.1 Update 1

VMware Virtual Disk Development Kit 5.5

Windows Azure SDK for Java 2.0

zlib 1.2.8

The following Arcserve UDP Agent (Linux) license agreements are available in the \Bookshelf_Files\TPSA folder in the CA arcserve Unified Data Protection Knowledge Center: